Add the struct ipc_user descriptor (and its ipc_user_pdata slot in struct
ipc) that the IPC4 kernel handler uses to forward commands to the
user-space IPC thread: the two IPC4 message words, the reply fields, and
a user-readable copy of the resolved comp_driver + tr_ctx used by
user-space component creation.

In ipc4 helper, allow component buffers to be allocated from the LL user
heap (ipc->ll_alloc) and create them on the component's configured core
rather than the current CPU, so buffer creation works from the user
thread when CONFIG_SOF_USERSPACE_LL is enabled.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

…stic

Extract the per-message processing logic for module CONFIG_GET/SET and
LARGE_CONFIG_GET/SET into standalone functions that return their results
via output parameters instead of writing the global msg_reply directly,
and give SET_PIPELINE_STATE external linkage.

This is a pure refactor with no functional change. The new
ipc4_process_module_config(), ipc4_process_large_config_get(),
ipc4_process_large_config_set() and ipc4_set_pipeline_state() can be
called from any execution context, which is needed to later dispatch
these messages from a separate IPC user-space thread.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

The IPC reply and compound-message completion entry points need to be
callable from the IPC user-space thread. Declare ipc_msg_reply(),
ipc_compound_pre_start(), ipc_compound_post_start() and
ipc_wait_for_compound_msg() as Zephyr syscalls when
CONFIG_SOF_USERSPACE_LL is enabled, renaming the implementations to
z_impl_* and adding z_vrfy_* verification wrappers. A new ipc_reply.h
carries the ipc_msg_reply declaration so it can be pulled in as a
syscall header.

Register the new syscall headers in CMakeLists.txt. No functional change
for non-userspace builds, where the functions keep direct external
linkage via z_impl_* defines.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

The pipeline, component and chain-DMA bookkeeping objects must be
reachable from the user-space IPC thread, so allocate them from the
system user heap via sof_heap_alloc()/sof_heap_free() instead of the
generic rzalloc()/rfree(). As sof_heap_alloc() does not zero the
allocation, add an explicit memset() to preserve the previous behaviour.

Give ipc4_add_comp_dev() external linkage (declared in topology.h) so the
user thread can register a created component, and skip the buffer tr_ctx
copy for user-space LL builds where the kernel tr_ctx is not mapped.

No functional change for non-userspace builds.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

The user-space IPC thread reads the IPC4 module init parameter block
directly from MAILBOX_HOSTBOX_BASE (comp_new_ipc4() / comp_new_ipc4_user()),
so the HOSTBOX region must be reachable from the user LL memory domain.

Map two partitions when CONFIG_SOF_USERSPACE_LL && CONFIG_IPC_MAJOR_4:
an uncached read-only view for the parameter reads, and a cached RW view
because the sys_cache_data_invd_range() syscall verifier requires write
access to the invalidated range.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Add function user_ll_grant_access() to allow other threads
to access the scheduler mutex. This is needed if work is submitted
from other threads to the scheduler.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Add a dedicated user-space thread for handling IPC commands that operate
on audio pipelines when CONFIG_SOF_USERSPACE_LL is enabled. This provides
only the protocol-agnostic infrastructure:

 - ipc_user_init() creates the K_USER thread, allocates its k_sem/k_event
   handshake objects, sets up the memory domain and access grants, and
   spins up the LL scheduler context.
 - ipc_user_forward_cmd() forwards the two raw IPC message words from the
   kernel IPC handler to the user thread via k_event signaling, sets
   IPC_TASK_IN_THREAD so the host is not signaled until the user thread
   completes, and collects the result through a k_sem handshake.
 - ipc_user_thread_fn() runs the wait loop and delegates the actual
   command interpretation to ipc_user_thread_dispatch(), a __weak hook
   overridden by the active IPC major.

No IPC-major-specific knowledge lives here; the IPC4 dispatch is added in
a following commit. The generic infra can be extended to cover other IPC
protocol variants.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Add comp_new_ipc4_user(), called from the user-space IPC thread to create
a component from user context. It receives a pre-resolved driver pointer
from the kernel handler (which does the privileged IMR manifest / driver
list lookup), parses the IPC4 init-instance message, reads the module
init parameter block from the HOSTBOX, and calls drv->ops.create() so
untrusted module init code does not execute with kernel privileges.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Provide the IPC4 implementation of ipc_user_thread_dispatch(), the
protocol-specific hook called from the generic user-space IPC thread. It
reconstructs the IPC4 message from the forwarded primary/extension words
and runs the privilege-separated portion of each supported command:
pipeline create/delete/set-state, module config get/set, large-config
get/set, bind/unbind, and init/delete instance. Component creation goes
through comp_new_ipc4_user() so module code runs in user context.

This moves the IPC4 command switch out of the protocol-agnostic
ipc-common.c into the IPC4 handler where it belongs.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Route the IPC4 commands that operate on audio pipelines to the user-space
IPC thread via ipc_user_forward_cmd() when CONFIG_SOF_USERSPACE_LL is
enabled: create/delete/set-state pipeline, config get/set, large-config
get/set, bind/unbind and init/delete instance.

For MOD_INIT_INSTANCE the kernel still resolves the driver (needs IMR
manifest access) and copies comp_driver + tr_ctx into the user-readable
ipc_user buffer before forwarding; cross-core creation stays in kernel.
LARGE_CONFIG get/set for base firmware (module_id 0) also stay in kernel
because they touch the IMR manifest. CONFIG_GET / LARGE_CONFIG_GET copy
the reply extension (and tx payload) back from the user thread.

The now-unused ipc4_new_pipeline()/ipc4_delete_pipeline() kernel helpers
are compiled out in the user-space configuration.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

If CONFIG_SOF_BOOT_TEST_STANDALONE is set, ipc_init() is terminated
early. This ensures SOF will not start to generate or respond
to IPC messages that could potentially interfere with standalone
test cases (some of which send and receive IPCs).

The current implementation leaves the component list uninitialized
and this can cause trouble to standalone tests that want to utilzie
common IPC code to build messages.

Fix this problem by executing more of ipc_init() also in the standalone
mode.

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>